Skip to main content

November 25

· 4 min read

In this section, you will find: Reference to new StackSpot features & relevant documentation changes.

Features

Centralized Secrets Management

With this new feature, users with the Account Holder and Account Admin profiles can now use a unified interface to register, view, edit, and remove Secrets at all levels of StackSpot, such as Organization, Workspace, and Spot (StackSpot AI).

This ensures security, centralized governance, and ease of use in managing sensitive credentials, reducing the risk of leaks or misuse.

Improvements

New Sidebar Item Organization

Navigation in the StackSpot Account Portal sidebar is now simpler and more intuitive. The changes include adjustments to the sidebar structure, revised naming conventions, and removal of categories.

Cancellation of Scheduled Secret Deletion

It is now possible to cancel the scheduled deletion of a Secret in StackSpot before the 30-day period ends. With this update, during the 30-day deletion scheduling period, you can cancel the deletion and resume using the Secret on the StackSpot platform.

Output data in run steps in the StackSpot Workflow

With the added support, now reusable type Workflows can also generate output data in Steps of type run. For example, now in the script field of your run Step you can use the following syntax:

echo nome_output=valor_output >> $STK_OUTPUTS

Example:

Set a value for the output:

echo environment_name='development' >> $STK_OUTPUTS

Check the page with more details on how to generate outputs with the Workflow

New Schema v4 and support for input scope for Plugins

This improvement will discontinue the use of environment variables in the inputs-envs field in Plugins on StackSpot. The use of inputs-envs will be replaced by the input scope present in the StackSpot Workflow, but limited to the default and env scopes.

What has changed?

  • The schema version of your Plugin must be updated from version v3 to v4:
schema-version: v4
kind: plugin
metadata:
  name: my-plugin
#...
#...
#...
  • The inputs-envs must be replaced with the input syntax using scope: env:

By default, a Plugin input that does not have the scope: env defined will be considered as scope: default, and its behavior will not be changed.

The env scope determines the behavior of the Workflow input and now of Plugins as an environment input. This way, you can define a different value for the Plugin input based on the environments available in your Workspace.

You should update your input using inputs-envs:

spec:
  inputs-envs:
    - label: SQS Arn
      name: sqs_arn
      type: text

To scope: env

spec:
  inputs:
   - type: text
     name: sqs_arn
     scope: env
     label: "SQS Arn" 
   ... other inputs ...
  • Behavior of commands for Plugins:

stk create plugin

  • Added support for manifest v4 for Plugins.
  • It is now possible to define inputs with the default and env scopes.
  • If the scope is not informed, the default will be default.
  • Support for the inputs-envs field in the manifest has been removed.

stk apply plugin and stk apply plugin --deploy

  • Interactive mode adjusted to handle inputs of different scopes.
  • Non-interactive mode updated to accept options like --name.input "value".
  • Added the possibility to pass inputs via --inputs-json or -i.
  • Parameters --spec and spec_file now support the new scopes.

stk update plugin

  • In interactive mode, default values are filled in for inputs with both scopes.
  • Validation of the functioning of **scope: default** for inputs of types required-connection and generated-connection.
  • In non-interactive mode, ensured support for --inputs-json and -i.