-
Notifications
You must be signed in to change notification settings - Fork 324
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
New command: m365 spe container activate #6086
Labels
Comments
Adam-it
added
new feature
needs peer review
Needs second pair of eyes to review the spec or PR
labels
Jun 9, 2024
@pnp/cli-for-microsoft-365-maintainers any feed or could we open this up? |
Nice one! Here I would also clarify the description a bit more. Good catch with the additional information. We should really make sure that this is added as a remark. |
Adam-it
added
help wanted
and removed
needs peer review
Needs second pair of eyes to review the spec or PR
labels
Jul 15, 2024
Can I work on it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Usage
m365 spe container activate [options]
Description
Activates a container
Options
-i, --id <id>
Examples
Activates a container
m365 spe container activate --id "b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z"
Default properties
No response
Additional Info
We should point out in the docs the following:
Container is created in an inactive state, as indicated by the status property. A container must be activated within 24 hours after creation, or it will be automatically deleted. Upon activation, the value of the status property changes from inactive to active.
A Container can be activated by calling the activate API, or any other API that updates or modifies the Container or its content. For example, uploading a file to a Container, adding permission to a Container, creating a custom property on a Container, or updating the properties of a Container can activate it.
we may use the following
POST
request:https://learn.microsoft.com/en-us/graph/api/filestoragecontainer-activate?view=graph-rest-1.0&tabs=http
The text was updated successfully, but these errors were encountered: