LRN UX for HQ IAM.
See & copy the LRN of an IAM resource (User, Group, Service Account, Role).
LRN is also an available column in all IAM listing pages. You can enable it in the column selector of the table.
Environments + metrics columns.
Tables UX update: powerful grid
Multi sort
Reorder of columns + column selection
Filters
Preferences are saved for the user
CLI
Provide shell completion for agent --env flag
IAM - Updated permissions syntax.
Renaming. Some services and resources have been renamed. This is to simplify and make the IAM model more consistent. You can find the latest spec here. You may need to adjust your policy YAML definitions. Reach out to us if you need help.
Prefix/infix wildcard support. You can now use *
in a prefix or infix position for resource-id path segments. Use this to express things like "environments that end in -dev" (*-dev
) or "topics whose name starts with fraud and ends with analytics" (fraud*analytics
).
Improved Global SQL studio UX
Topic navigator IDE experience.
See latest topic messages by default, ordered by time, with latest messages 1st.
Dark mode for sign-in page
User Profile page now correctly save changes.
Expose Agent dashboard metrics via API.
Improved Agent-level navigation bar.
We have made new alpha release 17:
Agent image:
HQ image:
HQ CLI image
New Helm version 17 for agent and for the HQ: https://lenses.jfrog.io/ui/native/helm-charts-preview/
When working on software projects, there often arises a need to create additional environment variables for various purposes. One common scenario for this is when users need to securely handle sensitive information, such as passwords or API keys. By storing a user password in a secret, the system ensures that such sensitive information is not exposed to unauthorized access, and this practice offers enhanced security.
Property restPort
has been removed and replaced by lensesHq.http.address
In the provisioning, there has been slight adjustment in the parent agent configuration parameter.
Changes:
lenses has been renamed to lensesAgent
As provisioning with the latest version (2) is mandatory for successful running of the agent, both configs are removed.
In the the past it was possible to use H2 database which would be instantly deployed and ready to use alongside the agent.
Due to certain performance limitations which come with H2 database which can impact the agent functionality, we decided to completely remove H2 support.
However, persistence parameter still remains and can be used to enable extra volume creation dedicated specifically just logs.