Skip to content

[New Resource] api_key_project_assignment #3198

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

aristosvo
Copy link

@aristosvo aristosvo commented Mar 22, 2025

Description

Please include a summary of the fix/feature/change, including any relevant motivation and context.

Link to any related issue(s):
Resolves #2030

Type of change:

  • Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
  • New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR. A migration guide must be created or updated if the new feature will go in a major version.
  • Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR. A migration guide must be created or updated.
  • This change requires a documentation update
  • Documentation fix/enhancement

Required Checklist:

  • I have signed the MongoDB CLA
  • I have read the contributing guides
  • I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
  • I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
  • I have added any necessary documentation (if appropriate)
  • I have run make fmt and formatted my code
  • If changes include deprecations or removals I have added appropriate changelog entries.
  • If changes include removal or addition of 3rd party GitHub actions, I updated our internal document. Reach out to the APIx Integration slack channel to get access to the internal document.

Further comments

@aristosvo aristosvo force-pushed the resource/api-key-project-assignment branch from b5a9fc2 to 6460e69 Compare March 27, 2025 14:06
@aristosvo aristosvo marked this pull request as ready for review March 27, 2025 14:07
@aristosvo aristosvo requested a review from a team as a code owner March 27, 2025 14:07
@marcosuma
Copy link
Collaborator

@aristosvo, thank you for your PR. While we can't merge this PR right away, we are considering what is the best solution to fix this issue. I've initiated a discussion with the team and we will try to make a decision.

@aristosvo
Copy link
Author

@marcosuma Thanks for letting me know. I'm not on a tight schedule here, but it would help for our future upgrade (still stuck at 1.11) and also restructuring our Terraform/organization of MongoDB.

Thanks in advance!

Copy link
Contributor

github-actions bot commented Apr 7, 2025

This PR has gone 7 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 7 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!

@github-actions github-actions bot added the stale label Apr 7, 2025
@aristosvo
Copy link
Author

bump

@github-actions github-actions bot removed the stale label Apr 8, 2025
Copy link
Contributor

This PR has gone 7 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 7 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!

@github-actions github-actions bot added the stale label Apr 13, 2025
@aristosvo
Copy link
Author

bump

@github-actions github-actions bot removed the stale label Apr 14, 2025
Copy link
Contributor

This PR has gone 7 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 7 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!

@github-actions github-actions bot added the stale label Apr 20, 2025
@aristosvo
Copy link
Author

bump

@github-actions github-actions bot removed the stale label Apr 22, 2025
Copy link
Contributor

This PR has gone 7 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 7 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!

@github-actions github-actions bot added the stale label Apr 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Assigning existing Organization API key to new/updated projects
2 participants