feat: remove the experiment flag for the sandbox commands and add new partner template IDs#512
feat: remove the experiment flag for the sandbox commands and add new partner template IDs#512
sandbox commands and add new partner template IDs#512Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #512 +/- ##
=======================================
Coverage 71.26% 71.27%
=======================================
Files 222 222
Lines 18682 18665 -17
=======================================
- Hits 13314 13303 -11
+ Misses 4187 4184 -3
+ Partials 1181 1178 -3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
At line 80 there was a recommendation to use charm for the 'Choose a Slack team where your email address matches...' info message; is charm stable yet, such that we can make that change?
There was a problem hiding this comment.
Huh (Charm) is now the default and only prompt library. So, if you're using a prompt then you're now using Charm's Huh :)
There was a problem hiding this comment.
yea perhaps we get rid of that comment?
There was a problem hiding this comment.
Ah, gotcha :) Updated to use the 'Help' config for the prompt instead of a separate log statement
| "it-incident-management": 4, | ||
| "customer-support": 5, | ||
| "sales": 6, | ||
| "marketing": 7, |
There was a problem hiding this comment.
This PR also adds mappings for the new partner templates
There was a problem hiding this comment.
Thanks @vegeris. In the future, it would be better for this to be a separate PR so that it can stand out in the GitHub Release Notes and Changelog.
suggestion: Can you please update the Changelog section of this PR Description so that the documentation team knows to document it on docs.slack.dev.
There was a problem hiding this comment.
suggestion: @vegeris Can you please add these to the Long Description so that developers can discover the partner template Ids that are available to use?
There was a problem hiding this comment.
I wasn't sure if we would want to highlight it in the Long Description as the grand majority of users would be regular non-partner developers; for the list command for example, we only add the 'sandbox type' label to partner sandboxes to reduce visual noise for regular sandboxes
document it on docs.slack.dev
Speaking of, I'd like to double check the process for getting new commands documented. My current assumption was that we would have a brief announcement in the Changelog through this PR and that once these changes are included in a release, that I would post in #api-docs to get the commands documented on docs.slack.dev?
There was a problem hiding this comment.
Also, if there's a strong preference I can apply the changes unrelated to removing the experiment flag first and then come back to this PR
sandbox commandssandbox commands
mwbrooks
left a comment
There was a problem hiding this comment.
🙏🏻 Thanks for removing the experiment @vegeris
✏️ I've left a few change request suggestions. In the future, I'd encourage the PR to only remove the experiment and add other additions in separate PRs. It allows both the documentation team to spot changes easier and our GitHub Release Notes (based on PR titles) to communicate the changes to our developers.
| "it-incident-management": 4, | ||
| "customer-support": 5, | ||
| "sales": 6, | ||
| "marketing": 7, |
There was a problem hiding this comment.
Thanks @vegeris. In the future, it would be better for this to be a separate PR so that it can stand out in the GitHub Release Notes and Changelog.
suggestion: Can you please update the Changelog section of this PR Description so that the documentation team knows to document it on docs.slack.dev.
| "it-incident-management": 4, | ||
| "customer-support": 5, | ||
| "sales": 6, | ||
| "marketing": 7, |
There was a problem hiding this comment.
suggestion: @vegeris Can you please add these to the Long Description so that developers can discover the partner template Ids that are available to use?
There was a problem hiding this comment.
Huh (Charm) is now the default and only prompt library. So, if you're using a prompt then you're now using Charm's Huh :)
| ErrDotEnvFileRead = "dotenv_file_read_error" | ||
| ErrDotEnvFileWrite = "dotenv_file_write_error" | ||
| ErrDotEnvVarMarshal = "dotenv_var_marshal_error" | ||
| ErrDomainLong = "domain_long" |
There was a problem hiding this comment.
suggestion: Can this please be prefixed with ErrSandboxDomainLong = "sandbox_domain_long" so that we know it's part of the Sandbox error codes. You'll need to reorganize it alphabetically.
There was a problem hiding this comment.
💯 Updated this error code and alphabetized the sandbox error codes added previously!
sandbox commandssandbox commands and add new partner template IDs
Changelog
This is effectively the release of the
sandboxcommands and should be highlighted in the changelog:Summary
This PR removes the experiment flag currently required to run the sandbox commands
Testing
Instead of:
We can run:
Requirements