Add in CodeArtifact tool flags to modify login behaviour

[whardier]

Is your feature request related to a problem? Please describe.
Pip and other CodeArtifact login tools need to modify login behaviour through the use of flags. Immediate use case is to alter which configuration setting is used with pip tool in order to avoid pulling through codeartifact upstreams (they are problematic) as well as speed up installation process (codeartifact is also slow)

Describe the solution you'd like
I've provided PR #6633 to best describe the solution. Allow for --flags and provide some fairly generic choices.

Describe alternatives you've considered
using --dry-run and sed to alter the command.. this is not a secure approach.

Additional context
Let's speed up build/deploy and make devs lives a smidge easier when utilizing CodeArtifact.

[kdaily]

Hi @whardier,

Thanks for your post and the pull request. The CodeArtifact commands for the AWS CLI are maintained by the CodeArtifact team. I'll let them know about this suggestion. I'm not familiar with how this command works. Having an example of what you do now (with --dry-run and sed) and how your proposed change works to solve this would be helpful.

I can't provide a timeframe when the CodeArtifact team will be able to review, but I'll update when I hear something.

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.

[whardier]

Hmm. The close out process seems sub-optimal.

[stealthycoin]

Yea sorry about that. I'm going to re-open it. We have a new process for prioritizing contributions to review #6828 detailing improvements to the contributing process. So I will be re-opening the issue for tracking interest, and marking the PR as draft until the criteria in the new process is met.

[tim-finnigan]

Thanks for your patience, it looks like this fell off of our radar. I'll try reaching out to the CodeArtifact team again to review this and share their feedback.

[tim-finnigan]

Thank you for the feature request and the proposed PR #6633. A member of the CodeArtifact team has reviewed your submission and has the following feedback:

The implementation in PR #6633 is quite specific, introducing a single new flag for pip/twine. The team's goal is to find a balance between simplicity/ease of use and the ability to customize. In this case, they feel the specific flag you've proposed represents a more advanced configuration than what the average user would require. As an alternative, the team suggests leveraging the existing AWS CLI commands aws codeartifact get-repository-endpoint and aws codeartifact get-authorization-token. This would allow users who need this level of customization to retrieve the necessary information and incorporate it into their own configuration commands. This approach offers more flexibility than the specific flag introduced in the PR.

While the team appreciates that your PR #6633 addresses the immediate need, they believe a more generic and extensible solution would better serve the broader customer base in the long run. This issue is not prioritized or planned at this time, but let us know if you have any further questions or suggestions for alternative solutions, and we may revisit this at a later date.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.