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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation for role-to-assume #161

Open
GrantBirki opened this issue Dec 21, 2023 · 0 comments
Open

Documentation for role-to-assume #161

GrantBirki opened this issue Dec 21, 2023 · 0 comments

Comments

@GrantBirki
Copy link

馃憢 Hi there!

I have a few projects that use GitHub Action's to publish to RubyGems. I am trying to adapt my projects to use the new "Trusted Publishing" via OIDC and want to adopt this Action in my workflow. My workflows are unique and I cannot just use the standard release-gem workflow.

I was looking over the docs here and it is not clear to me where the role-to-assume values come from. I'm looking for some updated documentation around this value in the following ways:

  • I see in the docs that role-to-assume can be 2 or 3. What do these numbers mean?
  • Where do these values come from?
  • What are the key differences between these "roles"?
  • What are the bare minimum roles / values that need to be provided for a GitHub Actions workflow to push a new Gem version to RubyGems.

Thanks! 馃檱

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

No branches or pull requests

1 participant