artifact definition example is reversed

[barriejc]

With artifact definition formatted as shown in Creating an artifact in Infrahub guide, no artifact is created in Infrahub from corresponding repo. Related .j2 template and .gql query from this repo can be found in Infrahub, and render just fine with infrahubctl.

Conversely, the artifact definition in the demo edge repo here works. Between name: and artifact_name: , they are reversed regarding which one is plain text vs. the one that's a slug/human friendly id (no spaces). In other words, for the docs this is shown, and doesn't work:

artifact_definitions:
  - name: "device_configuration"
    artifact_name: "Device configuration file"

vs. the demo edge repo, which works (no spaces in artifact_name):

artifact_definitions:
  - name: "Openconfig Interface for Arista devices"
    artifact_name: "openconfig-interfaces"

[petercrocker]

Can someone on @opsmill/customer-success have a look at this one?

[barriejc]

Thanks, @petercrocker. I created PR 55 for this as well, don't see a way to link it otherwise.

[FragmentedPacket]

Hi @barriejc, I attempted to reproduce this issue, but I wasn't able to.

Do you have a link to the repo you created to see the issue?

[barriejc]

I linked the demo edge repo above, but here's where the artifact_definition starts.

This conflicts with the formats shown in the documentation for name and artifact_name.

Here is what worked for me, which is the same format as in infrahub demo edge. When it didn't work, the formats were reversed like in the docs.

[barriejc]

Hi @FragmentedPacket, in order to try and move this bug and PR to the infrahub repo where it ought to have been created, I tried to reproduce this today in a fresh install of infrahub using the infrahub-demo-dc-fabric repo and I could not do so. Didn't matter whether it was name or artifact_name with spaces or not, it worked either way. It seems there was something weird about that particular lab set up then...? If I hadn't found the demo repo with the alternate use, however, I would probably have given up on ever getting that working, so I wonder if offering the suggestion to try swapping them (or just not using any spaces in either) would help someone?

[petercrocker]

I'm fixing this in: opsmill/infrahub#7476