Hi all,
With MUAO going strong, we are excited to start putting out development updates to share the features that we have been hard at work building as they roll out into the early access program. This will be an incremental process, with features and changes coming through as they’re ready.
Thank you so much for all of your testing and feedback on MUAO and its features up until this point. We look forward to hearing your responses so that we can build better and more usable tools together.
With the preamble aside, I’m excited to share with you the new functionality being released to our early access program this week.
Custom environments
It’s here, the big new feature that we believe will make concurrent development of apps faster and easier: custom environments. All EAP participants who upgrade to the latest CLI version can start using a new command:
forge environment create
This will prompt you to name a new development environment that can be used distinctly from the current default ‘development’ environment. This new development environment can be used for deployment, installation, and for tunnelling. For more information on custom environments, see: http://developer.atlassian.com/platform/forge/contributors/#custom-environments
Audit log events
Audit log events are now available, giving more visibility into the activities of your app compared to before.
In the developer console, a new tab called “Contributors” has been added. By accessing this tab you can see all of the additions and removals of contributors. This is the first of a number of audit log events we’ll be introducing to the developer console. The upcoming events which will be released at later dates are in the ‘Coming soon’ section below.
Each add contributor or remove contributor audit log is rendered to a single row displaying what type of contributor change happened, and who initiated it.
For more information about these logs, see: http://developer.atlassian.com/platform/forge/manage-app-contributors/.
Other changes
- Fixed a bug where only the owner of an app can consent to an app in the development environment. All Contributors are now able to do so.
Coming soon
- Restricting sensitive app permissions to the app owner
- Currently, all contributors to an app have almost the same permissions and abilities as each other. With this new feature, we’re now restricting app deletion and the addition and removal of contributors to just the app owner.
- Transferring app ownership
- Currently, the only way to transfer the ownership of a Forge app is by submitting a ticket and waiting for the Marketplace support team to action the request. With this new feature, app owners can now instantly transfer the ownership of an app to another contributor.
- Changes in app ownership will be rendered as rows under the ‘Contributors’ tab. This lets you see each time a change of ownership took place and who initiated it.
- Default app Environments
- Currently, when using custom environments, you need to specify the environment using a
-eflag for thedeploy, install, and tunnelcommands. - We will be adding a new command to set a default environment that will be automatically applied to the
deploy, install, and tunnelcommands without using the-eflag. This is set locally per contributor allowing contributors to have different default environments.
- Currently, when using custom environments, you need to specify the environment using a
- Viewing deployment audit logs
- The ‘Deployments’ tab displays each of the deployment events across all environments, whether successful or not.
- Each audit log is rendered as a single row, where you can see the corresponding timestamp, the user deploying a new version, the environment to which the deployment was made, and the deployment status.
- Filtering metrics and logs by each dev environment
- Currently, you can filter metrics and logs by development, staging, and production environments. Soon, however, you’ll be able to filter by each of the dev environments created.