taras

openapi: 3.0.3
info:
  title: 'backstage-plugin-changes-backend'
  version: '1'
  description: The Backstage backend plugin that provides the Changes API
  contact: {}
servers:
  - url: /
  - url: changes
components:

taras

openapi: 3.0.3
info:
  title: 'backstage-plugin-changes-backend'
  version: '1'
  description: The Backstage backend plugin that provides the Changes API
  contact: {}
servers:
  - url: /
  - url: changes
components:

taras

import axios, { AxiosInstance } from 'axios';
import dotenv from 'dotenv';
import {
    IncrementalEntityProvider,
    EntityIteratorResult,
} from '@backstage/plugin-catalog-backend-module-incremental-ingestion';

dotenv.config();

interface BitbucketApiResponse {

taras

Formats

We would like Global Ember Meetup to be a platform for members of the Ember community to keep each other update to date on progress they make in the Ember activities. So, we encourage speakers to return and give updates on previous talks.

We have 2 main formats for videos in Global Ember Meetup.

Introduction to <addon_name> format

These talks are typically 15-20 minutes with the purpose of introducing an addon to the Ember community. These talks usually answer Why was this addon created? When should it be used? What should the user be aware of? The result is video that looks like these and they can be added to video README of the addon. For example, see ember-cp-validations or ember-state-service.

taras

function useComposer() {
  const github = // useApi(Scm)
  const token = github.token
  
  return {
    async getRepositories() {
      return fetch(.../repositoriess)
    },
    async getFeatures() {
      return fetch(.../features)

taras

import fs from 'fs/promises';
import path from 'path';
import { findPaths } from '@backstage/cli-common';
import { Command } from 'commander';
import { loadConfig, loadConfigSchema } from '@backstage/config-loader';
import { getPackages } from '@manypkg/get-packages';
import { ConfigReader } from '@backstage/config';

async function inject() {
  const config = await readConfig(process.argv);

taras

import { findPaths } from '@backstage/cli-common';
import { Command } from 'commander';
import { loadConfig, loadConfigSchema } from '@backstage/config-loader';
import { getPackages } from '@manypkg/get-packages';
import { ConfigReader, Config } from '@backstage/config';

export async function readConfig(argv: NodeJS.Process['argv']) {
  const program = new Command();
  program.option('--config <path>', 'Config files to load instead of app-config.yaml', []);

taras

catalog:
  <AboutCard>:
    $import:
      - names: [<AboutCard>]
        from: ./catalog.yaml
      - names: [<Alarm>]
        from: ./icons.yaml
    $do:
      $<AboutCard>:
        secondaryButtons(_):

taras

query EnvironmentsView($cursor: String) {
  @table
  environments(first: 10, after: $cursor) {
    nodes {
      ... on Environment {
        name
        namespace
        deployment {
          name
          createdBy

taras

query AllOrganizations($organization: String!, $endCursor: String) {
  organizations(first: 100, after: $organization) {
    pageInfo { 
      hasNextPage
      endCursor 
    }
    nodes {
      ... OrganizationNode
      ... on Organization {
        repositories(first: 100, after: $endCursor) {