Skip to content

Conversation

kporter101
Copy link
Collaborator

How to read this pull request

Artifactory schema has been updated to reflect that an identity token should now be used for auth instead of username/ API token.

Checklist

  • The commit message includes an explanation of the changes
  • Manual validation of the changes have been performed (if possible)
  • New or modified code has requisite test coverage (if possible)
  • I have performed a self-review of the changes
  • I have made necessary changes and/or pull requests for documentation
  • I have written useful comments in the code
  • Version file/release label updated, if release needed

Description: docCaretToBacktick(`
- ^artifactory.username^ (String) The Artifactory API username. This will likely be your hashicorp email address
- ^artifactory.token^ (String) The Artifactory API token. You can sign into Artifactory and generate one
- ^artifactory.token^ (String) The Artifactory identity token. You can get one by joining the 'artifactory-users' Doormat
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's change our single quotes to be carets and they'll get interpreted into backticks in the rendered markdown.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also think that maybe we should merge this as part of the change where we make username optional. then we could put deprecated by it. 🤔

@kporter101 kporter101 force-pushed the VAULT-38191/remove-artifactory-user branch from 67ac3ec to 60516d9 Compare August 8, 2025 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants