Skip to content

Tags: juju/description

Tags

v8.0.1

Toggle v8.0.1's commit message
Release v8.0.1

v8.0.0

Toggle v8.0.0's commit message
Release v8.0.0

v7.0.2

Toggle v7.0.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #152 from SimonRichardson/expose-application-setters

#152

It's handy to expose the application getters and setters. That way we can work with the interface.

v7.0.1

Toggle v7.0.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #151 from SimonRichardson/charm-actions

#151

Import/export charm actions, config, and lxd-profiles for a given charm. These represent the actual files that can be found in a charm. We require these configuration files, so that when we import a 3.6 or 4.0 model into a 4.0 controller, we can correctly infer all of the RI (referential integrity) when creating applications.

v7.0.0

Toggle v7.0.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #151 from SimonRichardson/charm-actions

#151

Import/export charm actions, config, and lxd-profiles for a given charm. These represent the actual files that can be found in a charm. We require these configuration files, so that when we import a 3.6 or 4.0 model into a 4.0 controller, we can correctly infer all of the RI (referential integrity) when creating applications.

v6.3.0

Toggle v6.3.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #147 from SimonRichardson/charm-metadata-manifest

#147

When migrating 3.6 to 4.0 we need to have the charm metadata and manifest upfront when importing an application. This is a requirement in order to keep RI (referential integrity) for the new SQL schema. The metadata and manifest are treated as an amorphous type, not as individual leaf types for every type of the metadata. This means when we want to rev the metadata it will be done at the root level (metadata and manifest only have a version).

Otherwise, the code is a replication of https://github.com/juju/juju/tree/main/internal/charm. Versioning of the charm will now impact model import/export. Changing the charm metadata is no longer free (probably never was, but always treated as such).

----

JIRA: [JUJU-6411](https://warthogs.atlassian.net/browse/JUJU-6411)


[JUJU-6411]: https://warthogs.atlassian.net/browse/JUJU-6411?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

v6.2.0

Toggle v6.2.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #145 from wallyworld/merge-v5-20240710

#145

Merge v5 into v6, no conflicts.

#144 [from wallyworld/add-secret-checksum](e21a788)

v5.2.0

Toggle v5.2.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #144 from wallyworld/add-secret-checksum

#144

Secret entities get a new field to record the checksum of the latest revision.
The export version is changed to 2. Things like access, consumer info just thunk to the v1 method.

[JIRA-6225](https://warthogs.atlassian.net/browse/JUJU-6225)

v6.1.0

Toggle v6.1.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #141 from tlm/v5-to-v6

V5 to v6

v5.1.0

Toggle v5.1.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #140 from tlm/agent-version-in-root

Introduces agent version as a top level key.