Auth not being picked up correctly in GitHub Action using Artifactory and self hosted runners

Describe the bug

I’m trying to validate a canary release that is running on a self hosted runner which pulls dependencies from a private Artifactory npm registry and then subsequently publishes a package back to it, all through a GitHub action that is on a self hosted runner. Everything seems to be working correctly except the publish step itself, and I’m seeing the following:

Subsequently, further down:

I don’t necessarily have access to the runner environment as that is managed by our ops team but I have verified the following:

• The action runs in /home/ubuntu/actions-runner/_work/fe-ui/fe-ui
• The .npmrc file seems to be updated with the token entry correctly
  • //artifactory.internal.livongo.com/artifactory/api/npm/npm-repository/:_authToken=${NPM_TOKEN}
• The .npmrc file that is being updated with the above token lives inside of /home/ubuntu/.npmrc

To Reproduce

Expected behavior

Screenshots

Environment information:

Additional context

I would love to provide any additional info but I don’t have much more to go off of. WHat can I do to add additional details that may help resolve this?

[reintroducing]

@hipstersmoothie Thank you for being patient while we figured this out.

[hipstersmoothie]

Yeah I’m fine with that. If you come up with some good artifactory setup step we can add it to the docs too