```Python hl_lines="15"
    {!> ../../../docs_src/body_nested_models/tutorial008.py!}
    ```

## Editor support everywhere

And you get editor support everywhere.

Even for items inside of lists:

<img src="/img/tutorial/body-nested-models/image01.png">

You couldn't get this kind of editor support if you were working directly with `dict` instead of Pydantic models.

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package org.gradle.tooling.model.kotlin.dsl;


/**
 * Severity of an editor report.
 *
 * @since 6.0
 */
public enum EditorReportSeverity {
    WARNING,
    ERROR

    return 1
  fi

  # Finally, the users configuration will not be respected.
  echo_blue "Changes the user makes should be overwritten by kube-addon-manager"
  EDITOR="sed -i 's/50m/600m/'" kubectl edit limits/limits -n ${TEST_NS}
  if kubectl get limits/limits -n ${TEST_NS} -o yaml | grep --silent "50m"; then
    error "failed to edit resource with sed -- test is broken"
    return 1
  fi

 * limitations under the License.
 */

package org.gradle.tooling.model.kotlin.dsl;

import javax.annotation.Nullable;


/**
 * Report to the editor.
 *
 * @since 6.0
 */
public interface EditorReport {

    EditorReportSeverity getSeverity();

    String getMessage();

    @Nullable
    EditorPosition getPosition();

/test.out
/test/garbage/*.out
/test/pass.out
/test/run.out
/test/times.out

# This file includes artifacts of Go build that should not be checked in.
# For files created by specific development environment (e.g. editor),
# use alternative ways to exclude files from git.

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package org.gradle.tooling.model.kotlin.dsl;


/**
 * Position in the editor.
 *
 * @since 6.0
 */
public interface EditorPosition {

    int getLine();

    int getColumn();

`[PROJECT_NUMBER]******@****.***`) includes the following roles:

* **Kubernetes Engine Admin** (`roles/container.admin`)
* **Editor** (`roles/editor`, included by default)

## Step 2: Set up a cluster

The following steps are automated with the script `create_cluster_gke.sh` located in this directory. To create a cluster with the script, simply run:

```bash

	//   * 'kubernetes.io/h2c' - HTTP/2 prior knowledge over cleartext as described in https://www.rfc-editor.org/rfc/rfc9113.html#name-starting-http-2-with-prior-
	//   * 'kubernetes.io/ws'  - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455
	//   * 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455
	//
	// * Other protocols should use implementation-defined prefixed names such as

// of a frame (just above the architectural stack pointer).
// It is zero on x86 and PtrSize on most non-x86 (LR-based) systems.
// On PowerPC it is larger, to cover three more reserved words:
// the compiler word, the link editor word, and the TOC save word.
const MinFrameSize = goarch.MinFrameSize

// StackAlign is the required alignment of the SP register.
// The stack must be at least word aligned, but some architectures require more.

Kubernetes-defined prefixed names:\n  * 'kubernetes.io/h2c' - HTTP/2 prior knowledge over cleartext as described in https://www.rfc-editor.org/rfc/rfc9113.html#name-starting-http-2-with-prior-\n  * 'kubernetes.io/ws'  - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455\n  * 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455\n\n* Other protocols should use implementation-defined prefixed names such as mycompany.com/my-custom-protocol.",...