Skip to content

docs: add sso okta + jumpcloud configurations#340

Open
quetzalliwrites wants to merge 4 commits intomainfrom
docs-aws-sso-okta
Open

docs: add sso okta + jumpcloud configurations#340
quetzalliwrites wants to merge 4 commits intomainfrom
docs-aws-sso-okta

Conversation

@quetzalliwrites
Copy link
Collaborator

No description provided.

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Dec 4, 2025

Deploying localstack-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: a405ce1
Status: ✅  Deploy successful!
Preview URL: https://1472bc2d.localstack-docs.pages.dev
Branch Preview URL: https://docs-aws-sso-okta.localstack-docs.pages.dev

View logs

@quetzalliwrites quetzalliwrites changed the title docs: aws sso okta configuration docs: add sso okta + jumpcloud configurations Dec 4, 2025
@quetzalliwrites
Copy link
Collaborator Author

Poke @lukqw 😸

Copy link
Member

Choose a reason for hiding this comment

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

Question: this seems duplicated from the screenshot above?

Copy link
Member

Choose a reason for hiding this comment

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

Question: Would it make sense to split this based on provider?
We already have a separate page for Azure AD.

@lukqw
Copy link
Member

lukqw commented Jan 9, 2026

poke @quetzalliwrites 😄

@quetzalliwrites
Copy link
Collaborator Author

@HarshCasper tyvm!

@quetzalliwrites
Copy link
Collaborator Author

@HarshCasper we have updated screenshots now, @lukqw redid them. Let us know if this looks good now :)

Copy link
Collaborator Author

@quetzalliwrites quetzalliwrites left a comment

Choose a reason for hiding this comment

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

Hey @HarshCasper, I see the build is failing, why is this npm module giving a 404? 🤔


No wrangler.toml file found. Continuing.
--
10:54:20.821 | Detected the following tools from environment: npm@10.9.2, nodejs@22.16.0
10:54:20.822 | Installing project dependencies: npm clean-install --progress=false
10:54:30.155 | npm error code E404
10:54:30.155 | npm error 404 Not Found - GET https://registry.npmjs.org/starlight-toc-overview-customizer/-/starlight-toc-overview-customizer-0.1.0.tgz - Not found
10:54:30.155 | npm error 404
10:54:30.156 | npm error 404  'starlight-toc-overview-customizer@https://registry.npmjs.org/starlight-toc-overview-customizer/-/starlight-toc-overview-customizer-0.1.0.tgz' is not in this registry.
10:54:30.156 | npm error 404
10:54:30.156 | npm error 404 Note that you can also install from a
10:54:30.156 | npm error 404 tarball, folder, http url, or git url.
10:54:30.157 | npm error A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2026-02-10T09_54_21_173Z-debug-0.log
10:54:30.189 | Error: Exit with error code: 1
10:54:30.189 | at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
10:54:30.189 | at Object.onceWrapper (node:events:652:26)
10:54:30.189 | at ChildProcess.emit (node:events:537:28)
10:54:30.189 | at ChildProcess._handle.onexit (node:internal/child_process:291:12)
10:54:30.199 | Failed: build command exited with code: 1
10:54:31.356 | Failed: error occurred while running build command

@remotesynth
Copy link
Collaborator

Hey @HarshCasper, I see the build is failing, why is this npm module giving a 404? 🤔


No wrangler.toml file found. Continuing.
--
10:54:20.821 | Detected the following tools from environment: npm@10.9.2, nodejs@22.16.0
10:54:20.822 | Installing project dependencies: npm clean-install --progress=false
10:54:30.155 | npm error code E404
10:54:30.155 | npm error 404 Not Found - GET https://registry.npmjs.org/starlight-toc-overview-customizer/-/starlight-toc-overview-customizer-0.1.0.tgz - Not found
10:54:30.155 | npm error 404
10:54:30.156 | npm error 404  'starlight-toc-overview-customizer@https://registry.npmjs.org/starlight-toc-overview-customizer/-/starlight-toc-overview-customizer-0.1.0.tgz' is not in this registry.
10:54:30.156 | npm error 404
10:54:30.156 | npm error 404 Note that you can also install from a
10:54:30.156 | npm error 404 tarball, folder, http url, or git url.
10:54:30.157 | npm error A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2026-02-10T09_54_21_173Z-debug-0.log
10:54:30.189 | Error: Exit with error code: 1
10:54:30.189 | at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
10:54:30.189 | at Object.onceWrapper (node:events:652:26)
10:54:30.189 | at ChildProcess.emit (node:events:537:28)
10:54:30.189 | at ChildProcess._handle.onexit (node:internal/child_process:291:12)
10:54:30.199 | Failed: build command exited with code: 1
10:54:31.356 | Failed: error occurred while running build command

This was recently fixed in main so a rebase should fixed.

@quetzalliwrites
Copy link
Collaborator Author

This was recently fixed in main so a rebase should fixed.

OMG THANK YOU @remotesynth, the AI bots didn't help on this one!

@quetzalliwrites
Copy link
Collaborator Author

Hola @lukqw and @remotesynth, can you folks please give this a final review? The screenshots are updated, feedback addressed, and build is fixed 😸

Copy link
Collaborator

@remotesynth remotesynth left a comment

Choose a reason for hiding this comment

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

I don't view it as a blocker for this update per se, but I'd love to explore a cleaner way to annotate these images.

@lukqw
Copy link
Member

lukqw commented Feb 13, 2026

@quetzalliwrites I don't see my commit on the PR anymore, and it seems to have been reverted by the force push.
Any clue on what might have happened? Happy to add the commit again with the new screenshots.

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.

3 participants