IT Environments
DigiUsher IT Environments provide a signle point to manage your production and test environments. These resources are meant to be acquired for exclusive utilization by an organization member or a team member only temporarily and then released making them available again. The common use cases are release stands and demo environments where the availability of a range of components (e.g. for deploying some software version) has to be controlled in order to eliminate accidental breaking or loss of interconnections.
Depending on your cloud platform, there are two ways to create an Environment in the product:
- If you have a connected Cloud Account, you can easily mark the resources as Environments
- Or you can simply add new Environment, not related to any connected Cloud Account, from the Environments page
Mark existing cloud resources as Environments
At first, when an Organization is added into DigiUsher, the section is empty and new Environments have to be created manually by a user with the Organization Manager role from the scope of shareable resources that can only include Instances or DigiUsher clusters.
To be able to manage your cloud resource as environment, select the resource on the Resources page and click Mark as Environment.
The marked environment will appear on the Environments page. The resource is now available for booking, and you can proceesd with using webhooks and integrating with your CI/CD.
Create new Environment
To create a new Environment in DigiUsher select Environments at the left sidebar of the main page and click Add.
You will be prompted to input a Name and a Resource type for a new Environment.
A newly created entity will be added to this section and listed in a table providing information about a Pool that it belongs to, its Status which can be In use or Available, Upcoming bookings, related Software and Jira tickets (optional).
The following action buttons allow to control an existing environment:
- An Environment can be booked for a selected period of time.
- A booked Environment can be released to make it available again. A notification will be sent to the corresponding tenant user.
- A scope of resources can be deactivated temporarily to prohibit it from being booked.
- Deletion of the Environment.