-
Notifications
You must be signed in to change notification settings - Fork 275
Add onboarding content for Temporal Cloud #1410
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
Conversation
docs/cloud/how-to-manage-certificate-filters-in-temporal-cloud.md
Outdated
Show resolved
Hide resolved
docs/cloud/how-to-manage-certificate-filters-in-temporal-cloud.md
Outdated
Show resolved
Hide resolved
- The signing algorithm must include SHA-256 or stronger. | ||
SHA-1 and MD5 signing algorithms are rejected. | ||
|
||
When a client presents an end-entity certificate, and the whole certificate chain is constructed, each certificate in the chain (from end-entity to the root) must have a unique Distinguished Name (DN). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might need to link to documentation on what DN means? Example: https://knowledge.digicert.com/generalinformation/INFO1745.html (if we can find a better document or codify that ourselves, that's probably better)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The exhaustive definition is in section 9.5 of ITU-T X.501, but it's not exactly light reading. Trying to boil it down to the level we need is tricky. I'll keep hunting for a more accessible definition (to which we can link, if from a reputable source, or that I can use as inspiration for an inline definition).
docs/cloud/index.md
Outdated
## Information | ||
|
||
- [Account-level Roles](/cloud/what-are-the-account-level-roles-for-users-in-temporal-cloud) | ||
- [Namespace-level permissions](/cloud/what-are-the-namespace-level-permissions-for-users-in-temporal-cloud) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for consistency, why aren't these called Namespace-level Roles?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Roles apply to people (or at least their user accounts); permissions apply to objects.
docs/cloud/index.md
Outdated
|
||
## Upgrade policy | ||
|
||
All customers will automatically be upgraded to the latest minor version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this Upgrade Policy applies to the Cloud at all as the version we are running is managed by us and completely transparent to the end-user. I would just remove this entire section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rylandg, what's our current guidance on upgrade policy for Temporal Cloud?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mastermanu how would you specify SDK release updates as they relate to the upgrading we are doing?
While its true we havent changed our underlying api with sdk versions, we frequently questions about how our own upgrading impacts their SDK versioning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can and should mention SDK compatibility with the Cloud. But this specific section doesn't appear to mention anything related to SDKs and seems to have been meant more for the server, which doesn't apply here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So my understanding is that we are continuously upgrading Temporal Cloud, so this is an important statement. Cloud = OSS Server upgrades, so we should probably link out to a page that describes the Server / SDK compatibility caveats.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For expediency, I'm dropping this section for now. We can address it properly after this iteration of the onboarding guide goes live.
docs/cloud/what-are-the-account-level-roles-for-users-in-temporal-cloud.md
Outdated
Show resolved
Hide resolved
docs/cloud/what-are-the-account-level-roles-for-users-in-temporal-cloud.md
Outdated
Show resolved
Hide resolved
docs/cloud/what-are-the-account-level-roles-for-users-in-temporal-cloud.md
Outdated
Show resolved
Hide resolved
docs/cloud/what-are-the-account-level-roles-for-users-in-temporal-cloud.md
Outdated
Show resolved
Hide resolved
docs/cloud/what-are-the-namespace-level-permissions-for-users-in-temporal-cloud.md
Outdated
Show resolved
Hide resolved
docs/cloud/what-are-the-namespace-level-permissions-for-users-in-temporal-cloud.md
Outdated
Show resolved
Hide resolved
…ralio/documentation into djmagee/cloud-onboard-plus
This reverts commit 6f162b3.
…ralio/documentation into djmagee/cloud-onboard-plus
docs/cloud/what-are-the-account-level-roles-for-users-in-temporal-cloud.md
Show resolved
Hide resolved
…ralio/documentation into djmagee/cloud-onboard-plus
Preview
https://deploy-preview-1410--mystifying-fermi-1bc096.netlify.app/cloud
What does this PR do?
Add a whole bunch of content to support the new onboarding guide and creates true generated guides.