Skip to content

OIDC for external feeds #1207

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

Merged
merged 7 commits into from
Apr 28, 2025
Merged

OIDC for external feeds #1207

merged 7 commits into from
Apr 28, 2025

Conversation

grace-rehn
Copy link
Contributor

@grace-rehn grace-rehn commented Apr 16, 2025

About

This is a post about...

OIDC authentication for external feeds, particularly AWS Elastic, Azure and Google container registry feeds. This allows customers to set up their external feeds without static credentials avoiding secret rotation.

In this blog post, I walk through why OIDC authentication is useful and give a brief summary of how to set up each feed type. I have not gone into too much detail in each section and have linked the docs for more information.

[sc-105004]

Release

2025.2

Blog image idea

The design team will work on a design for the blog image. Add any ideas you have about the graphic image here. (Tegan will request the image from design and add it to the post when it's ready.)
Please note that the design team asks for a 1–2 week turnaround time.

Before you submit your post

Check everything off this list before you submit your post for review.

  • I'm familiar with the Octopus voice and style, the guide for blog content basics, and writing educational content.
  • I've checked the content using Grammarly (Octopus has a corporate license) and the Hemingway app to remove typos, grammatical errors, and passive voice.
  • The PR build passes validation, and if it doesn't, I've checked the common validations errors and none of those apply.
  • The images I've included follow the rules for working with images.
  • I've added alt text for all the images I've included (alt text describes an image to people unable to see it, 125 characters max)
  • The draft is complete and this post is ready to be reviewed. (Please mark the post 'ready for review' at the bottom of the PR.)
  • I've dropped a note in Slack in #topic-content-marketing to let Tegan Ali know my post is ready for review. (No need to fill out a content brief.)

How to review this PR

If there's anything you'd like reviewers to focus on, mention it here.

Publication date

If there are considerations for when to publish this post, mention them here. For example, "This post is supporting material for a webinar I'm conducting on [date], or this post should not get published until after a specific release on [date]."

Copy link

@wlthomson wlthomson left a comment

Choose a reason for hiding this comment

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

Awesome 🎉 !

A couple of really small improvements, mainly because I couldn't find anything significant to fault 😆 .

Reads really nicely and tells a strong story. Nice job!

@grace-rehn grace-rehn marked this pull request as ready for review April 16, 2025 05:40
@grace-rehn grace-rehn requested a review from TeganAli as a code owner April 16, 2025 05:40
@TeganAli TeganAli merged commit 7c953e4 into master Apr 28, 2025
3 checks passed
@TeganAli TeganAli deleted the grace/oidc-external-feeds branch April 28, 2025 05:54
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.

4 participants