Skip to content
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

[FEATURE] Adds the ability to add Externald and Tags to boto3_options of TupleS3StoreBackend #10075

Closed

Conversation

rosspb3
Copy link

@rosspb3 rosspb3 commented Jul 2, 2024

boto3_options of TupleS3StoreBackend now supports external_id and tags which gets passed to the sts assume_role call as ExternalId and Tags. This will support greater cross-account role policy scenarios.

Resolves #10272

  • Description of PR changes above includes a link to an existing GitHub issue
  • PR title is prefixed with one of: [BUGFIX], [FEATURE], [DOCS], [MAINTENANCE], [CONTRIB]
  • Code is linted - run invoke lint (uses ruff format + ruff check)
  • Appropriate tests and docs have been updated

For more information about contributing, see Contribute.

After you submit your PR, keep the page open and monitor the statuses of the various checks made by our continuous integration process at the bottom of the page. Please fix any issues that come up and reach out on Slack if you need help. Thanks for contributing!

…sume-role call for greater flexibility in using cross-account roles.
…sume-role call for greater flexibility in using cross-account roles.
…ature/aws_external_id

# Conflicts:
#	great_expectations/data_context/store/tuple_store_backend.py
#	tests/data_context/store/test_store_backends.py
Copy link

netlify bot commented Jul 2, 2024

👷 Deploy request for niobium-lead-7998 pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 7aa71ab

@gx-cla-bot
Copy link

gx-cla-bot bot commented Jul 2, 2024

A new contributor, HUZZAH! Welcome and thanks for joining our community. In order to accept a pull request we require that all contributors sign our Contributor License Agreement. We have two different CLAs, depending on whether you are contributing to GX in a personal or professional capacity. Please sign the one that is applicable to your situation so that we may accept your contribution:

Individual Contributor License Agreement v1.0
Software Grant and Corporate Contributor License Agreement v1.0

Once you have signed the CLA, you can add a comment with the text @cla-bot check and the bot will update the PR status!

Please reach out to the #gx-community-support channel, on our Slack if you have any questions or if you have already signed the CLA and are receiving this message in error.

Users missing a CLA: rosspb3

@rosspb3
Copy link
Author

rosspb3 commented Jul 2, 2024

@cla-bot check

@molliemarie
Copy link
Contributor

Hello @rosspb3. With the launch of Great Expectations Core (GX 1.0), we are closing old PRs posted regarding previous versions. Moving forward, we will focus our resources on supporting and improving GX Core (version 1.0 and beyond). If you find that an issue or PR you previously reported still exists in GX Core, we encourage you to resubmit it against the new version. With more resources dedicated to community support, we aim to tackle new issues swiftly. For specific details on what is GX-supported vs community-supported, you can reference our integration and support policy.

To get started on your transition to GX Core, check out the GX Core quickstart (click “Full example code” tab to see a code example).

Thank you for being part of the GX community and thank you for submitting this issue. We're excited about this new chapter and look forward to your feedback on GX Core. 🤗

@rosspb3
Copy link
Author

rosspb3 commented Aug 27, 2024

Hello @molliemarie, I did create a new feature request and updated the PR with the issue number and the latest code from the develop branch as the issue still exists with the latest code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add the ability to specify ExternalId and Tags in the boto3_options of TupleS3StoreBackend
3 participants