DOCSLIB.ORG

Codeartifact-User.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Codeartifact-User.Pdf CodeArtifact CodeArtifact User Guide CodeArtifact: CodeArtifact User Guide Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. CodeArtifact CodeArtifact User Guide Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. CodeArtifact CodeArtifact User Guide Table of Contents What is AWS CodeArtifact? ................................................................................................................. 1 How does CodeArtifact work? ..................................................................................................... 1 Concepts ................................................................................................................................... 1 Domain ............................................................................................................................. 2 Repository ......................................................................................................................... 2 Package ............................................................................................................................ 2 Package version ................................................................................................................. 2 Package version revision ..................................................................................................... 2 Upstream repository ........................................................................................................... 2 Asset ................................................................................................................................ 3 Package namespace ............................................................................................................ 3 How do I get started with CodeArtifact? ....................................................................................... 3 Setting up ......................................................................................................................................... 4 Sign up for AWS ........................................................................................................................ 4 Install or upgrade and then configure the AWS CLI ......................................................................... 4 Provision an IAM User ................................................................................................................. 5 Install your package manager or build tool ................................................................................... 6 Getting started .................................................................................................................................. 7 Prerequisites .............................................................................................................................. 7 Getting started using the console ................................................................................................ 7 Getting started using the AWS CLI ............................................................................................... 9 Working with repositories .................................................................................................................. 14 Create a repository ................................................................................................................... 14 Create a repository (console) ............................................................................................. 14 Create a repository (AWS CLI) ............................................................................................ 15 Create a repository with an upstream repository .................................................................. 16 Connect to a repository ............................................................................................................ 16 Use a package manager client ........................................................................................... 16 Delete a repository ................................................................................................................... 17 Delete a repository (console) ............................................................................................. 17 Delete a repository (AWS CLI) ............................................................................................ 17 List repositories ........................................................................................................................ 17 List repositories in an AWS account .................................................................................... 18 List repositories in the domain ........................................................................................... 18 View or modify a repository configuration ................................................................................... 20 View or modify a repository configuration (console) ............................................................. 20 View or modify a repository configuration (AWS CLI) ............................................................ 21 Repository policies .................................................................................................................. 22 Create a resource policy to grant read access ....................................................................... 22 Set a policy ..................................................................................................................... 23 Read a policy ................................................................................................................... 24 Delete a policy ................................................................................................................. 24 Grant read access to principals ........................................................................................... 24 Grant write access to packages .......................................................................................... 25 Grant write access to a repository ...................................................................................... 26 Add an external connection ....................................................................................................... 26 Add an external connection to a repository ......................................................................... 26 Supported external connection repositories ......................................................................... 27 Remove an external connection ......................................................................................... 27 Fetch npm packages from an external connection ................................................................ 28 Fetch Maven packages from an external connection .............................................................. 29 npm ingestion behavior .................................................................................................... 30 Maven ingestion behavior .................................................................................................. 31 CodeArtifact behavior when an external repository is not available ......................................... 31 iii CodeArtifact CodeArtifact User Guide Availability of new package versions ................................................................................... 32 Tag a repository ....................................................................................................................... 32 Tag repositories (CLI) ........................................................................................................ 32 Tag repositories (console) .................................................................................................. 34 Working with upstream repositories ................................................................................................... 38 Add, update, or remove upstream repositories (console) ................................................................ 38 Add, update, or remove upstream repositories (AWS CLI) ............................................................... 39 Requesting a package version with upstream repositories .............................................................. 40 Package retention from upstream repositories ..................................................................... 40 Fetch packages through an upstream relationship ................................................................ 40 Package retention in intermediate repositories ..................................................................... 42 Upstream repository priority order ............................................................................................. 42 Simple priority order example ............................................................................................ 43 Complex priority order example ......................................................................................... 43 API behavior with upstream repositories ....................................................................................
Load more

Recommended publications
  • Asp Net Jquery Ajax Json Example Wersja
    Asp Net Jquery Ajax Json Example Conquering and exculpatory Thorsten wited clumsily and prickle his heed unforcedly and soothingly. Unanswered and numinous Graig never conscripts observably when Bela shoals his luffas. Oligarchic and ben Ashton held so rifely that Simon sticky his bajada. Dbcontect classes to help, i am glad you will send ajax call will execute and the feedback. Scheduled tasks in asp jquery example will help make them together with an array of products table that will decrease automatically. Provides the asp net jquery json helper method, what the about. Via json format in asp net example given by microsoft json request is given by default name to your network have your data has a formatted result. Comment is shown the asp ajax json request to understand concept is the project, the article we click on the product details. Loads data types, ajax example is, the other articles. Into our method in asp net example we can get request and suggestions will not the future of response, for this by both the _layout. We should then the asp net ajax methods of errors potentially introduced by using chart with razor page without updating the class as an array of the div tag. Developer will call with jquery ajax json or with my things, then passes the database and the body. Message using and the example is the client side method can be the console. Year passed to use jquery json data you know what follows is providing different types in the year. Installing a controller folder and a button to products model, simple example below is, and then the _layout.
    [Show full text]
  • Front-End Development with ASP.NET Core, Angular, And
    Table of Contents COVER TITLE PAGE FOREWORD INTRODUCTION WHY WEB DEVELOPMENT REQUIRES POLYGLOT DEVELOPERS WHO THIS BOOK IS FOR WHAT THIS BOOK COVERS HOW THIS BOOK IS STRUCTURED WHAT YOU NEED TO USE THIS BOOK CONVENTIONS SOURCE CODE ERRATA 1 What’s New in ASP.NET Core MVC GETTING THE NAMES RIGHT A BRIEF HISTORY OF THE MICROSOFT .NET WEB STACK .NET CORE INTRODUCING ASP.NET CORE NEW FUNDAMENTAL FEATURES OF ASP.NET CORE AN OVERVIEW OF SOME ASP.NET CORE MIDDLEWARE ASP.NET CORE MVC SUMMARY 2 The Front‐End Developer Toolset ADDITIONAL LANGUAGES YOU HAVE TO KNOW JAVASCRIPT FRAMEWORKS CSS FRAMEWORKS PACKAGE MANAGERS TASK RUNNERS SUMMARY 3 Angular in a Nutshell ANGULAR CONCEPTS THE LANGUAGE OF ANGULAR SETTING UP AN ANGULAR PROJECT THE STRUCTURE OF AN ANGULAR APP DATA BINDING DIRECTIVES SERVICES AND DEPENDECY INJECTION MULTIPLE COMPONENTS INPUT AND OUTPUT PROPERTIES TALKING TO THE BACK END USING ANGULAR WITH ASP.NET MVC VISUAL STUDIO 2017 SUPPORT FOR ANGULAR SUMMARY 4 Bootstrap in a Nutshell INTRODUCTION TO BOOTSTRAP BOOTSTRAP STYLES COMPONENTS JAVASCRIPT CUSTOMIZING BOOTSTRAP WITH LESS BOOTSTRAP SUPPORT IN VISUAL STUDIO 2017 AND ASP.NET CORE SUMMARY 5 Managing Dependencies with NuGet and Bower GENERAL CONCEPTS NUGET NPM (NODE.JS PACKAGE MANAGER) BOWER SUMMARY 6 Building Your Application with Gulp and webpack WHAT FRONT‐END BUILD SYSTEMS ARE FOR A DEEPER LOOK AT GULP INTRODUCTION TO WEBPACK VISUAL STUDIO 2017 AND BUILD SYSTEMS SUMMARY 7 Deploying ASP.NET Core THE NEW HOSTING MODEL OF ASP.NET CORE INSTALLING ON INTERNET INFORMATION SERVICES ON PREMISE
    [Show full text]
  • Xcode Package from App Store
    KH Computational Physics- 2016 Introduction Setting up your computing environment Installation • MAC or Linux are the preferred operating system in this course on scientific computing. • Windows can be used, but the most important programs must be installed – python : There is a nice package ”Enthought Python Distribution” http://www.enthought.com/products/edudownload.php – C++ and Fortran compiler – BLAS&LAPACK for linear algebra – plotting program such as gnuplot Kristjan Haule, 2016 –1– KH Computational Physics- 2016 Introduction Software for this course: Essentials: • Python, and its packages in particular numpy, scipy, matplotlib • C++ compiler such as gcc • Text editor for coding (for example Emacs, Aquamacs, Enthought’s IDLE) • make to execute makefiles Highly Recommended: • Fortran compiler, such as gfortran or intel fortran • BLAS& LAPACK library for linear algebra (most likely provided by vendor) • open mp enabled fortran and C++ compiler Useful: • gnuplot for fast plotting. • gsl (Gnu scientific library) for implementation of various scientific algorithms. Kristjan Haule, 2016 –2– KH Computational Physics- 2016 Introduction Installation on MAC • Install Xcode package from App Store. • Install ‘‘Command Line Tools’’ from Apple’s software site. For Mavericks and lafter, open Xcode program, and choose from the menu Xcode -> Open Developer Tool -> More Developer Tools... You will be linked to the Apple page that allows you to access downloads for Xcode. You wil have to register as a developer (free). Search for the Xcode Command Line Tools in the search box in the upper left. Download and install the correct version of the Command Line Tools, for example for OS ”El Capitan” and Xcode 7.2, Kristjan Haule, 2016 –3– KH Computational Physics- 2016 Introduction you need Command Line Tools OS X 10.11 for Xcode 7.2 Apple’s Xcode contains many libraries and compilers for Mac systems.
    [Show full text]
  • Reasonml Install Guide Fall 2019
    CS17 Integrated Introduction to Computer Science Hughes ReasonML Install Guide Fall 2019 Contents 1 Install Guide (Windows) 1 1.1 Installing Node . .1 1.2 WSL.............................................1 1.3 Configuring Visual Studio Code . .2 2 Install Guide (Mac OSX) 2 2.1 Installing Visual Studio Code . .2 2.2 Installing Various XCode Tools (NVM, Node) . .2 2.3 Configuring Visual Studio Code . .5 3 Using ReasonML 5 3.1 Configuring Your Project . .5 3.2 Compiling ReasonML . .5 3.3 Running ReasonML . .5 4 Reason Tools (Browser) 6 1 Install Guide (Windows) 1.1 Installing Node Click here to install Node. 1.2 WSL Follow this guide to install Windows Subsystem for Linux (WSL). Select the Linux Distribution choice Ubuntu, which has an orange icon. Open the "Command Prompt" on your machine and type the following command. This can take a long time to install fully. Let it sit for some time, even if it appears as if it’s not doing anything. Feel free to move on to other steps while it loads. npm install - g ocaml - reason - wsl CS17 ReasonML Install Guide Fall 2019 Inside of Visual Studio Code go to Settings > User Settings. In the upper right-hand corner, click on the icon that looks like a file with an arrow wrapped around it. A window should open up with a file in it. Copy and paste the following lines into the file in between the curly braces and save the file. "reason.path.bsb":"bash - ic bsb", "reason.path.ocamlfind":"bash - ic ocamlfind", "reason.path.ocamlmerlin":"bash - ic ocamlmerlin", "reason.path.opam":"bash - ic opam", "reason.path.rebuild":"bash - ic rebuild", "reason.path.refmt":"bash - ic refmt", "reason.path.refmterr":"bash - ic refmterr", "reason.path.rtop":"bash - ic rtop", "editor.formatOnSave": true, "reason.diagnostics.tools":["merlin","bsb"], "terminal.integrated.shell.windows":"C:\\\\WINDOWS\\\\System32\\\\bash.exe" After the initial install command has terminated, you can now open WSL (Ubuntu).
    [Show full text]
  • Iroha Handbook: Installation, Getting Started, API, Guides, and Troubleshooting
    Iroha handbook: installation, getting started, API, guides, and troubleshooting Hyperledger Iroha community Aug 24, 2021 TABLE OF CONTENTS 1 Overview of Iroha 3 1.1 What are the key features of Iroha?...................................3 1.2 Where can Iroha be used?........................................3 1.3 How is it different from Bitcoin or Ethereum?..............................3 1.4 How is it different from the rest of Hyperledger frameworks or other permissioned blockchains?...4 1.5 How to create applications around Iroha?................................4 2 Concepts and Architecture 5 2.1 Core concepts..............................................5 2.2 What’s inside Iroha?........................................... 13 3 Quick Start Guide 17 3.1 Prerequisites............................................... 17 3.2 Starting Iroha Node........................................... 17 3.3 Try other guides............................................. 19 4 Integrated Projects 29 4.1 Hyperledger Ursa............................................. 29 4.2 Hyperledger Explorer.......................................... 29 4.3 Hyperledger Burrow........................................... 30 5 Building Iroha 37 5.1 Prerequisites............................................... 37 5.2 Installing dependencies with Vcpkg Dependency Manager....................... 39 5.3 Build Process............................................... 40 6 Configure 45 6.1 Configure TLS for client-peer communication (torii).......................... 45 6.2 Deployment-specific
    [Show full text]
  • Manual De Iroha: Instalaci´On,Inicio, API, Gu´Iasy Resoluci´Onde Problemas Выпуск
    Manual de Iroha: instalaci´on,inicio, API, gu´ıasy resoluci´onde problemas Выпуск Comunidad Iroha Hyperledger янв. 26, 2021 Содержание 1 Overview of Iroha 3 1.1 What are the key features of Iroha?................................3 1.2 Where can Iroha be used?......................................3 1.3 How is it different from Bitcoin or Ethereum?..........................3 1.4 How is it different from the rest of Hyperledger frameworks or other permissioned blockchains?4 1.5 How to create applications around Iroha?.............................4 2 С чего начать 5 2.1 Prerequisites.............................................5 2.2 Starting Iroha Node.........................................5 2.3 Try other guides...........................................7 3 Use Case Scenarios 9 3.1 Certificates in Education, Healthcare...............................9 3.2 Cross-Border Asset Transfers.................................... 10 3.3 Financial Applications........................................ 10 3.4 Identity Management........................................ 11 3.5 Supply Chain............................................. 11 3.6 Fund Management.......................................... 12 3.7 Related Research........................................... 12 4 Ключевые концепции 13 4.1 Sections................................................ 13 5 Guides and how-tos 23 5.1 Building Iroha............................................ 23 5.2 Конфигурация........................................... 29 5.3 Deploying Iroha..........................................
    [Show full text]
  • Declare Module Typescript Library
    Declare Module Typescript Library Mahmud quintuplicate fantastically as untenantable Glynn grabbles her jays clot tribally. Measlier and noisier Matthias always scunges enlargedly and tessellating his mitzvahs. Undebauched Gunter enisled: he fledging his padauks philosophically and yore. Roughly speaking, how exactly do we make use of these declaration files in our code base? Not every component fully supports any component type you pass in. The compiler will accept JSX. Component Library is like any other NPM Module. Sometimes, I am exporting it to maintain symmetry with the other files. The types here are fine but they do not truly convey the meaning or intent of the code. Passing CLI arguments via shebang is allowed on Mac but not Linux. But they work differently. Software engineer taught me that a Startup product grows and develops every day. In this article, we are going to learn the structure of the Type Declaration files and their use cases. Mozilla and individual contributors. Now, this means something is wrong with the way PHPStorm interprets tsconfig. Typescript will then also export type definitions together with the compiled javascript code so the package can be used with both Typescript and Javascript. Either choice will solve your error. Dan is a big geek who likes making stuff with computers! Senior Front End Engineer at Modus Create. An introduction to TypeScript's module system techscouting. Plus, this should be true. How do I use it? Now that we have everything set up, etc. Once you have the clone URL, the Redux pattern is a radical departure from the style of programming we are used to.
    [Show full text]
  • Installing and Running Tensorflow
    Installing and Running Tensorflow DOWNLOAD AND INSTALLATION INSTRUCTIONS TensorFlow is now distributed under an Apache v2 open source license on GitHub. STEP 1. INSTALL NVIDIA CUDA To use TensorFlow with NVIDIA GPUs, the first step is to install the CUDA Toolkit. STEP 2. INSTALL NVIDIA CUDNN Once the CUDA Toolkit is installed, download cuDNN v5.1 Library for Linux (note that you will need to register for the Accelerated Computing Developer Program). Once downloaded, uncompress the files and copy them into the CUDA Toolkit directory (assumed here to be in /usr/local/cuda/): $ sudo tar -xvf cudnn-8.0-linux-x64-v5.1-rc.tgz -C /usr/local STEP 3. INSTALL AND UPGRADE PIP TensorFlow itself can be installed using the pip package manager. First, make sure that your system has pip installed and updated: $ sudo apt-get install python-pip python-dev $ pip install --upgrade pip STEP 4. INSTALL BAZEL To build TensorFlow from source, the Bazel build system must first be installed as follows. Full details are available here. $ sudo apt-get install software-properties-common swig $ sudo add-apt-repository ppa:webupd8team/java $ sudo apt-get update $ sudo apt-get install oracle-java8-installer $ echo "deb http://storage.googleapis.com/bazel-apt stable jdk1.8" | sudo tee /etc/apt/sources.list.d/bazel.list $ curl https://storage.googleapis.com/bazel-apt/doc/apt-key.pub.gpg | sudo apt-key add - $ sudo apt-get update $ sudo apt-get install bazel STEP 5. INSTALL TENSORFLOW To obtain the best performance with TensorFlow we recommend building it from source. First, clone the TensorFlow source code repository: $ git clone https://github.com/tensorflow/tensorflow $ cd tensorflow $ git reset --hard 70de76e Then run the configure script as follows: $ ./configure Please specify the location of python.
    [Show full text]
  • Fpm Documentation Release 1.7.0
    fpm Documentation Release 1.7.0 Jordan Sissel Sep 08, 2017 Contents 1 Backstory 3 2 The Solution - FPM 5 3 Things that should work 7 4 Table of Contents 9 4.1 What is FPM?..............................................9 4.2 Installation................................................ 10 4.3 Use Cases................................................. 11 4.4 Packages................................................. 13 4.5 Want to contribute? Or need help?.................................... 21 4.6 Release Notes and Change Log..................................... 22 i ii fpm Documentation, Release 1.7.0 Note: The documentation here is a work-in-progress. If you want to contribute new docs or report problems, I invite you to do so on the project issue tracker. The goal of fpm is to make it easy and quick to build packages such as rpms, debs, OSX packages, etc. fpm, as a project, exists with the following principles in mind: • If fpm is not helping you make packages easily, then there is a bug in fpm. • If you are having a bad time with fpm, then there is a bug in fpm. • If the documentation is confusing, then this is a bug in fpm. If there is a bug in fpm, then we can work together to fix it. If you wish to report a bug/problem/whatever, I welcome you to do on the project issue tracker. You can find out how to use fpm in the documentation. Contents 1 fpm Documentation, Release 1.7.0 2 Contents CHAPTER 1 Backstory Sometimes packaging is done wrong (because you can’t do it right for all situations), but small tweaks can fix it.
    [Show full text]
  • A Package Manager for Curry
    A Package Manager for Curry Jonas Oberschweiber Master-Thesis eingereicht im September 2016 Christian-Albrechts-Universität zu Kiel Programmiersprachen und Übersetzerkonstruktion Betreut durch: Prof. Dr. Michael Hanus und M.Sc. Björn Peemöller Eidesstattliche Erklärung Hiermit erkläre ich an Eides statt, dass ich die vorliegende Arbeit selbstständig ver- fasst und keine anderen als die angegebenen Quellen und Hilfsmittel verwendet habe. Kiel, Contents 1 Introduction 1 2 The Curry Programming Language 3 2.1 Curry’s Logic Features 3 2.2 Abstract Curry 5 2.3 The Compiler Ecosystem 6 3 Package Management Systems 9 3.1 Semantic Versioning 10 3.2 Dependency Management 12 3.3 Ruby’s Gems and Bundler 16 3.4 JavaScript’s npm 19 3.5 Haskell’s Cabal 21 4 A Package Manager for Curry 25 4.1 The Command Line Interface 26 4.2 What’s in a Package? 29 4.3 Finding Packages 35 4.4 Installing Packages 37 4.5 Resolving Dependencies 38 vi A Package Manager for Curry 4.6 Interacting with the Compiler 43 4.7 Enforcing Semantic Versioning 46 5 Implementation 51 5.1 The Main Module 52 5.2 Packages and Dependencies 56 5.3 Dependency Resolution 58 5.4 Comparing APIs 71 5.5 Comparing Program Behavior 73 6 Evaluation 85 6.1 Comparing Package Versions 85 6.2 A Sample Dependency Resolution 88 6.3 Performance of the Resolution Algorithm 90 6.4 Performance of API and Behavior Comparison 96 7 Summary & Future Work 99 A Total Order on Versions 105 B A Few Curry Packages 109 C Raw Performance Figures 117 D User’s Manual 121 1 Introduction Modern software systems typically rely on many external libraries, reusing func- tionality that can be shared between programs instead of reimplementing it for each new project.
    [Show full text]
  • Investigating the Reproducbility of NPM Packages
    Investigating the Reproducbility of NPM packages Pronnoy Goswami Thesis submitted to the Faculty of the Virginia Polytechnic Institute and State University in partial fulfillment of the requirements for the degree of Master of Science in Computer Engineering Haibo Zeng, Chair Na Meng Paul E. Plassmann May 6, 2020 Blacksburg, Virginia Keywords: Empirical, JavaScript, NPM packages, Reproducibility, Software Security, Software Engineering Copyright 2020, Pronnoy Goswami Investigating the Reproducbility of NPM packages Pronnoy Goswami (ABSTRACT) The meteoric increase in the popularity of JavaScript and a large developer community has led to the emergence of a large ecosystem of third-party packages available via the Node Package Manager (NPM) repository which contains over one million published packages and witnesses a billion daily downloads. Most of the developers download these pre-compiled published packages from the NPM repository instead of building these packages from the available source code. Unfortunately, recent articles have revealed repackaging attacks to the NPM packages. To achieve such attacks the attackers primarily follow three steps – (1) download the source code of a highly depended upon NPM package, (2) inject mali- cious code, and (3) then publish the modified packages as either misnamed package (i.e., typo-squatting attack) or as the official package on the NPM repository using compromised maintainer credentials. These attacks highlight the need to verify the reproducibility of NPM packages. Reproducible Build is a concept that allows the verification of build artifacts for pre-compiled packages by re-building the packages using the same build environment config- uration documented by the package maintainers. This motivates us to conduct an empirical study (1) to examine the reproducibility of NPM packages, (2) to assess the influence of any non-reproducible packages, and (3) to explore the reasons for non-reproducibility.
    [Show full text]
  • Greetings from Slackbuilds.Org
    Greetings from SlackBuilds.org David Spencer pkgsrcCon 2017 About SBo 11 years old conventional ports-inspired setup ● from source ftw ● shell script + metadata ~6500 packages disjoint from core Slackware (~1400 packages) lightweight project one new server, one old server About SBo ~250 maintainers active in last year ~12500 commits in last year no bugtracker no CI ● Infrastructure is a productivity killer ● Aggressively reductionist on dep management ● Vanilla from upstream, patch only when needed ● Don’t split packages ● git git baby About SBo submissions are open ambition to submit ‘something’ is a thing maintainers drop in and drop out review must be sympathetic volunteers are a pipeline not a funnel don’t crush people’s dreams maintainer is expert on the software reviewer (admin) is expert on good packaging no room for style variations About SBo Education needs to be a thing No time in review feedback hurts, doesn’t scale Currently done on mailing list & forum ● CI as education Listening systemd refugees rolling release ● stable versus current out of date / security / unmaintained upstream disappearing SBo maintainers disappearing sources and projects ● repology ● keeps mailing list active Happy community Users helping each other Tools Satellite projects Package all the obscure things ● if it exists it will attract users Unopened letter to the world Need to educate upstreams proper releases with proper tarballs don’t move or delete old tarballs learn to write a decent Makefile no, I don’t want your stinking CFLAGS don’t use -Werror
    [Show full text]