-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Managed Deployments: Groups and Releases #1653
base: main
Are you sure you want to change the base?
Managed Deployments: Groups and Releases #1653
Conversation
32abbc4
to
d34b3d2
Compare
1b97ac0
to
5b70ac5
Compare
4c72acc
to
995a8f8
Compare
5b70ac5
to
03e63ba
Compare
DeploymentGroups
and DeploymentReleases
03e63ba
to
dc97780
Compare
15dbf73
to
da17189
Compare
…platform when batch-updating (#1912) Previously, we displayed all deployments as options when batch-updating devices. This is confusing because you could see deployments that shouldn't be options. This PR now requires you to filter by platform first before having the ability to bulk move devices into a deployment. This change does create an extra step when moving devices to a deployment but it's important to note this is an interim feature before #1653 is finished.
7a56134
to
4bbcfb9
Compare
b2f510a
to
97f872c
Compare
alias NervesHub.ManagedDeployments.DeploymentGroup | ||
|
||
@spec audit_deployment_created(User.t(), DeploymentGroup.t()) :: :ok | ||
def audit_deployment_created(user, deployment_group) do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These function names should change, but they shouldn't just have _group
added to them. I want to make a more wholistic change to device template that removes the resource name from the function names, e.g. DeploymentGroupTemplates.audit_created
. We'll save that work for later.
@@ -360,28 +360,6 @@ defmodule NervesHub.Devices do | |||
end | |||
end | |||
|
|||
def get_eligible_deployments(%Device{firmware_metadata: nil}), do: [] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function was unused.
@@ -0,0 +1,15 @@ | |||
defmodule NervesHub.ManagedDeployments.InflightDeploymentCheck do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to rename as we're planning on keeping the term "deployments" to describe the literal process instead of a resource.
@@ -106,6 +106,10 @@ defmodule NervesHubWeb do | |||
|
|||
def page_title(socket, page_title), do: assign(socket, :page_title, page_title) | |||
|
|||
@spec sidebar_tab( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sneaking this in :)
97f872c
to
b9dd1e0
Compare
b9dd1e0
to
76fc857
Compare
This work contains two sets of changes: the creation of
DeploymentRelease
s and the renaming ofdeployments
todeployment_groups
.DeploymentRelease
integration will be done in the next body of work for managed deploys, this PR has become too big to add any more functionality.So many things have been renamed that it's easier to list what hasn't been renamed:
deployments
table namedeployments
in the namedeployment_id
foreign key in DB and application codeDatabase-related renaming will be done later. Pub sub topic and events should and will be adjusted, but this is not the time. It won't be a simple rename and needs more care and thought.