Your goal in this PR is to implement org-level storage CRUD endpoints. The design of the system and expected behavior is indicated in @vast-reimagined.md. The VAST API that we use is unique, with the documentation accessible within the HTML file at path: file:///Users/nshah/Downloads/VAST%20Management%20Service%20(VMS)%20REST%20API%20Version%207%20for%20VAST%20Cluster%205.3.html. The API is separated into the following categories: Introduction to the VMS REST API, Getting Started, User Permissions for Cluster, Tenant and Resource Access, Authentication, VMS Administrators, Infrastructure Element Store, Network Access, Data Engine, Data Protection, User Management, Database Analytics, Alarms and Events, Support, Schemas. Note: Do not run any git commands. Your goal is to implement this accurately and robustly with the behavior diagrammed in vast-reimagined. Ensure that all code is written cleanly, following patterns from the rest of the repository wherever possible.

Please analyze the changes in this PR and focus on identifying critical issues related to: - Potential bugs or issues - Performance - Security - Correctness - Style Style issues are going to be a bulk of the issues. They should be high priority, no matter how small. Watch for the following, as well as other style issues not specifically outline. The goal of this is to be an all encompassing agent - it's better to point out a small issue than for me to submit it and my team lead cares about it, meaning that if debating between whether or not to bring up an issue, just bring it up. Here are some style issue examples: 1. Using Single letter variables 2. Structs, function calls, or more that are passed in without reason 3. Code paths that are inefficient or have no purpose. 4. Recreating objects when they aren't used previously. 5. Pieces that are used but have negligible use 6. Align File Names 7. Decompose Large activities Again, this isn't an end all be all list of issues, these are just examples. The goal is to write code that is clean and intentional, where each line serves a purpose. Sign off with a checkbox emoji: (approved) or (issues found).

Edit this page @Logging. Reformat it by adding bolding, italics, underlines where relevant, change text color by highlighting pieces of text and changing them where it would fit best. Also adjust spelling and language errors Add images where possible, by entering /image, pressing on image, then searching unsplash. Do the same with mermaid code diagrams using /mermaid pressing Code (mermaid), then adding mermaid code. Clear up information in analogies whenever necessary @Cloud Software Development

Break this PDF down fully and completely. Explain the information using analogies and ensure that I know everything to ace a test. Show code examples, proper situations, and key pieces I might need to know.

Compile a list of steps I need to take to do this project. First, outline the project. Break it down into the key steps in a broad sense. Then, State the key objective. Finally, breakdown exactly how to complete the project step by step.

Review the explanation in LEARNINGS in relation to the code implementation in CODE The goal of this is for me to replicate this implementation from my understanding. Identify any gaps or missing elements in my understanding of the concepts. Specifically: 1. Clarify any cases and what the differentiating factors between them are. 2. Analyze all relevant cases in the code, providing clear definitions and examples for each concept 3. Highlight any additional key concepts that should be included in the explanation.

Enhance this command by providing the following details: - Add a clear, descriptive title. - Write a concise description that explains the purpose and expected outcome of the command. - Select the most appropriate category. - Add only relevant tags (avoid filler or loosely related tags). - Include notes that specify how and where the command should be executed (e.g., AI code editor, Comet, base browser), along with any additional context needed for proper usage.

You are a TA walking me through the steps of a project. Your goal is to help me understand exactly what to do and **why**. I will provide you with a project step that I'm unsure about, and you will provide me with an explanation in the following format: Steps Overview Outline of Requirements Explanation Steps (in-depth) Be very clear in explanation, but don't generate walls of text. For any code, explain what each line is doing. ``` [STEP] ```

Use this link and the project handout to break down and explain in detail: What is the main goal of this project? What specific features and system-level concepts are you expected to implement? What are the boundaries (what is not required)? Provide a clear summary that translates any formal requirements into plain, actionable objectives for students new to implementing Unix-like shells. Furthermore, walk through the key steps that the student needs to add. Assume that the student doesn't know anything. For anything that would require code implementations, outline clear code commands and be very specific about reasoning, all flags, and exactly why that command is needed

Take this text and pry and get inside my head. Try to translate stuff, and help me get to the bottom of what I'm thinking

For all the questions in this quiz, select the correct response, then click the confidence buttons to proceed to the next question. If you can't answer the question, output the correct answers here. This quiz is [number] questions long.

I've attached a project spec to this. Here is my task: 1. Outline the steps I need to take manually (outside of a code editor) to setup this project. 2. Design a series of prompts for me to feed into an AI to create this app. (Take into account anything I need to tell the AI from step 1.

You are a Teachers Assistant. Your job is to explain exactly what this project is trying to do in 3 different ways. 1. Objectives and Technical Explanation. What is the end goal? 2. Explain it to me like I'm 15 years old. 3. Break down the key technologies, edge cases, and anything else I need to keep in mind.

Evaluate whether this is a good deal by checking its price history over time, comparing current pricing across other major retailers, and analyzing recent customer reviews for patterns in quality, reliability, and satisfaction. Highlight any red flags or standout features, and let me know if now is the best time to buy or if I should wait for a better price.

Help me prepare for my next meeting by listing the participants, outlining the meeting goals and agenda, highlighting anything I should review or prepare, and suggesting questions I could ask. When selecting the meeting, ignore all-day events and any meetings without other participants. If any participants are external to my company, include a brief bio.